feat: disallow registration before epoch #3 #95
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
danielattilasimon
force-pushed
the
no-immediate-registration
branch
from
1871291 to
3903836
Compare
Timeline: - epoch 1: initial initiatives are in warmup - epoch 2: initial initiatives can be voted on - epoch 3: registration opens for new initiatives In practice, we will "skip" epoch 1 by deploying with `EPOCH_START` backdated by one `EPOCH_DURATION`, so that initial initiatives can be voted on right from the get-go.
danielattilasimon
force-pushed
the
no-immediate-registration
branch
from
3903836 to
531b6fd
Compare
bingen
approved these changes
Dec 5, 2024
| // | ||
| // The reason we want to initially disable registration is that there's not vote snapshot to base the registration | ||
| // threshold upon, thus registration would otherwise be possible without having any LQTY staked. | ||
| contract DeploymentTest is MockStakingV1Deployer { |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Timeline:
In practice, we will "skip" epoch 1 by deploying with
EPOCH_STARTbackdated by oneEPOCH_DURATION, so that initial initiatives can be voted on right from the get-go.